Feature: guest features #273
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Depending on the node, storage, config of the guest the clone, copy, snaspshot features might not be availible
this is to allow for future guest commands
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add functionality to check which features are enable for a guest system.
Work done:
*Client.CheckVmRef()bd6f10d 7c6d46cget guestcommand toget guest configd5a6ce3get guest featurecommand ca58b91GuestHasFeature()to check if the guest has a specific feature 11feae1ListGuestFeatures()to check all the features a guest has enabled 11feae1The reason
GuestHasFeature()andListGuestFeatures()exist is because only one feature can be checked at the time resulting in multiple API calls. For this reason I didn't incorporate it intoConfigQemuandConfigLxc.